Smart Platform for Programming Remote Keyless Devices

ABSTRACT

A platform for a programmable remote transmitter, designed, and programmed to perform single or multiple operations, optionally incorporated into a custom-made base that attaches to a smart phone case or other mobile devices. The remote transmitter is designed and activated via secured programming provided by an application on the user&#39;s mobile device, without the intervention of car dealers, locksmiths or using difficult manual processes. The remote transmitter can be attached to smart phones, mobile devices, or other suitable surfaces (e.g. a briefcase or a vehicle&#39;s dashboard) for safekeeping and accessibility.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims priority to provisional patent application, Ser. No. 62/698,391 entitled “Attachable Case Technology”, filed Jul. 16, 2018, which application is incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copy-right rights whatsoever. 37 CFR 1.71(d).

FIELD

At least some embodiments disclosed herein relate, in general, to programmable remote keyless devices and more specifically to smart platforms for programmable remote keyless devices.

SUMMARY

The present disclosure is directed to a platform that provides a user programmable remote transmitter, designed and programmed to perform single or multiple operations, for example, locking and unlocking an automobile, and starting an automobile. The remote transmitter can be used independently or incorporated into a custom-made base that attaches to a cell phone case or other devices, referred to herein as an Attachable Remote Key or ARK.

In an embodiment, there are two distinctive features of the technology: the remote transmitter within the ARK is designed and activated via secured programming without the intervention of car dealers, locksmiths, or difficult and complicated processes; and, optionally, the case of the ARK can be attached to smart phones, other mobile devices, or other suitable surfaces (e.g. a briefcase or a vehicle's dashboard) for safekeeping and accessibility.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.

FIG. 1 shows an overview of an embodiment of a platform for a user programmable attachable remote key (ARK) in accordance with present disclosure.

FIG. 2 shows a block diagram providing a high-level view of an embodiment of functions provided by an ARK App in accordance with the present disclosure.

FIG. 3 shows a block diagram of an embodiment of a process of configuring an ARK using an ARK App in accordance with the present disclosure.

FIG. 4 shows a block diagram of an embodiment of a process of changing options relating to an ARK using an embodiment of ARK App in accordance with the present disclosure.

FIG. 5 shows a block diagram of an embodiment of the operation of an ARK App and ARK device in accordance with the present disclosure.

FIG. 6 shows a block diagram of an embodiment of options provided by an ARK App in accordance with the present disclosure.

FIG. 7 shows an embodiment of an ARK in accordance with present disclosure attached to a smart phone case.

FIG. 8 shows the ARK of FIG. 7 disassembled where the base of the ARK is attached to a smart phone case and the circuit board that implements the functions of the ARK are visible.

FIG. 9 shows another embodiment of an ARK in accordance with present disclosure attached to a smart phone case.

FIG. 10 shows the base of the ARK of FIG. 9 from a side view attached to a smart phone case.

FIG. 11 shows various illustrative form factors that can be used for an ARK in accordance with the present disclosure.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding. However, in certain instances, well known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure are not necessarily references to the same embodiment; and, such references mean at least one.

Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.

The present invention is described below with reference to block diagrams and operational illustrations of methods and devices for smart platforms for programmable re mote keyless devices. It is understood that each block of the block diagrams or operational illustrations, and combinations of blocks in the block diagrams or operational illustrations, can be implemented by means of analogue or digital hardware and computer program instructions.

These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, ASIC, or other programmable data processing apparatus, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implements the functions/acts specified in the block diagrams or operational block or blocks.

In some alternate implementations, the functions/acts noted in the blocks can occur out of the order noted in the operational illustrations. For example, two blocks shown in succession can in fact be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality/acts involved.

For the purposes of this disclosure, the term “server” or “computing device” should be understood to refer to a service point which provides processing, database, and/or communication facilities. By way of example, and not limitation, the term “server” or “computing device” can refer to a single, physical processor with associated communications and data storage and/or database facilities, or it can refer to a networked or clustered complex of processors and associated network and storage devices, as well as operating software and one or more database systems and applications software which support the services provided by the server.

In various embodiments, servers and/or computing devices may be provided as virtual servers and computing devices, which may be provided by a cloud-based platform, such as, for example, the Google Cloud® platform or the IBM Cloud® platform. In various embodiments, databases may be hosted on cloud-based data storage which may be provided by a cloud-based platform, such as, for example, the Google Cloud® platform or the IBM Cloud® platform. In various embodiments, servers or computing devices may be capable of receiving, capturing, and transmitting audio and/or video data.

For the purposes of this disclosure, the term “mobile device” should be understood to refer to any kind of computing device that is designed to be easily carried by a user to any location of the user's choosing. Examples of a mobile device include a smart phone, a cell phone, a tablet computer, and a laptop computer. Mobile devices commonly include wireless communications capabilities such as, for example, cellular communications capabilities, or Wi-Fi, and may be additionally capable of being connected to a hardwired network, such as an Ethernet network. Mobile devices may additionally include cameras, and microphones, that enable users to capture and transmit audio and visual data via available networks. Mobile devices may additionally include short range wireless communications capabilities such as Bluetooth® or NFC.

For the purposes of this disclosure, the term “app”, “applications”, and “application software” are used interchangeably, and should be understood to refer to computer program code in machine readable form, which may be stored on computer-readable media, that is executable by a server, mobile device, or other type of computing device or cluster of computing devices (e.g. such as provided by a cloud platform or service). Such machine readable form may comprise, without limitation, source code in a computer programming language, interpreted source code, or source code compiled into machine language directly executable by a specific processor type.

For the purposes of this disclosure, the term “platform” should be understood to refer a framework on which applications may be run. Such a framework can include various computing devices, such as, for example, servers, mobile devices, and desktop computers, which may be networked with one another. A platform may also be understood to include software applications implementing various functions provided by the platform. In various embodiments, a platform may be implemented, in whole, or part, utilizing an underlying cloud-based platform such as the Google Cloud® platform or the IBM Cloud® platform.

For the purposes of this disclosure a computer-readable medium stores computer data, which data can include computer program code that is executable by a computer, in machine readable form. By way of example, and not limitation, a computer-readable medium may comprise computer-readable storage media, for tangible or fixed storage of data, or communication media for transient interpretation of code-containing signals.

Computer-readable storage media, as used herein, refers to physical or tangible storage (as opposed to signals) and includes without limitation volatile and non-volatile, removable and non-removable media implemented in any method or technology for the tangible storage of information such as computer-readable instructions, data structures, program modules or other data. Computer-readable storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory, or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other physical or material medium which can be used to tangibly store the desired information or data or instructions and which can be accessed by a computer or processor.

In various embodiments, the present disclosure is directed to a platform that provides a user programmable remote transmitter, designed and programmed to perform single or multiple operations, optionally incorporated into a custom-made base that attaches to smart phone cases or other devices. For the purposes of the present disclosure, embodiments of such user programmable remote transmitters will hereinafter be referred to as an Attachable Remote Keys or ARKs.

In an embodiment, the ARK targets automobile keyless entry and ignition systems. In various embodiments the base of the ARK may take the form of a complete phone case into which multiple car remotes could be incorporated. In an embodiment, a keyless home entry system or other remotes could also be included. In an embodiment, a full case could include a sleeve for a driver's license, a credit card, and a home key. In various embodiments, the ARK is capable of incorporating electronic advances to maintain market leadership. Illustrative physical embodiments are shown in FIG. 7-11 (discussed further below).

In an embodiment, there are two distinctive features of the technology: the remote transmitter within the ARK is designed and activated via secured programming without the intervention of car dealers, locksmiths or using difficult manual processes; and, optionally, the case of the ARK can be attached to smart phones, mobile devices, or other suitable surfaces (e.g. a briefcase or a vehicle's dashboard) for safekeeping and accessibility.

In various embodiments, the design of the systems and methods disclosed herein to do away with the need for a customer to travel to a dealer/locksmith for key fob programming and significantly reduce the expense. With ARK technology, anyone purchasing an ARK will be able to easily and securely self-program their keys.

In various embodiments, an ARK comes equipped with the ability to be controlled by the owner's smartphone. In other words, an ARK could be left in the vehicle and the user could access all the key fob's functions directly from their smart phone.

FIG. 1 shows an overview of an embodiment of a 100 system for a user programmable attachable remote key (ARK) 110 in accordance with present disclosure.

The technical components that make up the ARK platform are:

the ARK 110;

the ARK smart phone app (ARK App) on a user mobile device 130;

the ARK ODB2 peripheral 140;

ARK Cloud-Based Services 150.

In an embodiment, the ARK 110 is capable of wirelessly communicating 112 with a vehicle's 120 onboard computer, much as a standard key fob does, and communicating via a short range wireless protocol 114, such as the Bluetooth® protocol, with the user's mobile device 130, for example, a smart phone. In an embodiment, the user's mobile device 130 is further capable of wirelessly communicating with the ARK ODB2 adapter 140 via a short range wireless protocol 134, such as the Bluetooth® protocol, and via a mobile network, with ARK Cloud-Based Services 150.

In an embodiment, the ARK 110 looks, feels and operates just like any traditional vehicle key fob. However, there are two distinctive features of the technology: the remote transmitter of the ARK 110 is designed and activated via secured programming without the intervention of car dealers, locksmiths or difficult processes; and, the case of the ARK can be attached to a smartphone 130 or other mobile device, kept in purses or briefcases, purses, or attached to other suitable surfaces for safekeeping and accessibility.

In an embodiment, in addition to the normal circuitry logic to control the vehicles functions, the ARK is designed with additional technology that allows the communication from the ARK to any smartphone capable of supporting Bluetooth low energy (BILE or BLE) communications protocol (short-wavelength UHF in the ISM band from 2.4 to 2.485 GHz.)

In an embodiment, initial configuration and setup of the ARK 110 is attained by enabling the device while pressing the configuration button option (similar to the configuration of other Bluetooth accessories for smartphones). Once the ARK enters configuration mode, the user can pair it with their smartphone 130 and proceed with the rest of the ARK 110 setup.

In the BLE communications protocol, the ARK 110 operates as a Bluetooth peripheral device. The smart phone operates as a central device. In an embodiment, ARK devices 110 are factory programmed with a unique key and pre-registered in a database provided by ARK Cloud-Based Services 150 for security and history programmability tracking.

In an embodiment, the ARK does not need a smartphone to be operational; the smart phone 130 and ARK App are used for programing only, replacing the cumbersome present dealer/locksmith or owner programming.

In an embodiment, the ARK 110 operates on a coin cell battery. Under normal conditions and with the BLE turned off, the ARK will operate similarly to legacy devices and battery will have the same duration. In an embodiment, with the BLE enabled device, battery power will be limited to approximately 10-12 months.

In an embodiment, the platform includes an ARK App (not explicitly shown) installed on the user device 130. In various embodiments, the ARK App supports Android and iPhone smart phones.

In an embodiment, all users will be required to register with the platform's 100 ARK Cloud-Based Services 150 and create an account. In an embodiment, the registration process provided by the ARK Cloud-Based Services is used in order to track user, datetime, VIN, and ARK 110 programing history. In an embodiment, this will also prevent the unauthorized use of key reprograming or counterfeited products. In an embodiment, user registration with the ARK Cloud-Based Services 150 is also be available over a desktop web application.

In an embodiment, in order to provide requisite security, the registrant will need to provide name, address, mobile phone number, the registrant's vehicle's VIN, other security information, and the registrant's credit or debit card. Security will be provided by the consistency of all of these factors.

In an embodiment, once the user's smartphone 130 is paired with the ARK 110, ARK 110 programming is handled thru the ARK App. There will be no need to press any keys/buttons on the ARK. In an embodiment, once the ARK 110 has been successfully programmed and paired with a specific smartphone 130, it cannot be paired to any other device unless it is factory reset by the key owner.

In an embodiment, once the ARK 110 is operational, it can be used as an extension of the ARK App. In other words, all the same functions available on the ARK 110 will be available on the user's smartphone 130. In an embodiment, the ARK App enables the user's smartphone 130 to be able to track the location of their ARK 110 as long as users are within 300 ft of the ARK 110. In an embodiment, the ARK App enables the user's smartphone to measure the current battery life of the ARK 110 so the user can replace the battery before it dies.

In an embodiment, the ARK ODB2 peripheral 140 is a Bluetooth based ODB2 protocol compliant device. It plugs into the vehicle's 120 ODB2 computer port 122. All vehicles since 1996 have this port and they are typically located underneath the dashboard 124 of the vehicle 124.

The ARK ODB2 peripheral 140 is required when there are no other programing methods available from the vehicle's manufacturer or when a new set of keys are needed thus deleting or removing any previous programmed key codes from the vehicle's computer. The ARK ODB2 peripheral 140 however, can provide additional services and ease the configuration process. Once the device 140 is connected to the vehicle's 120 ODB2 port 122, using the ARK App, the user will be prompted to connect their smartphone 130. Once communication is established, the user's smart phone can automatically retrieve vehicle 120 information such as VIN, make and model.

In an embodiment, to configure a new ARK 110 using the ODB2 peripheral 140, the user will go thru the steps described herein, which will communicate to the vehicle's computer via the ARK ODB2 periphera1140 to erase any old keys the user desires to erase from the user's computer and program the new ARK 110. In an embodiment, ARK ODB2 peripheral 140 can also serve as a vehicle's 120 computer scanner and can also report engine or other error codes to the user's smartphone 130.

In an embodiment, ARK 110 and the ODB2 peripheral 140 both communicate with the vehicle's on-board computer during the programming process. In another embodiment, only the ARK 110 communicates with the vehicle's on-board computer during the programming process.

In an embodiment, all users' transactions during registration and configuration, as well as historical data, are securely stored on the ARK Cloud-Based Services 150. In an embodiment, when a user downloads the ARK App to their smartphone 130 and registers, an account is created for the user with the ARK Cloud-Based Services 150. Once a user configures an ARK 110, it will be tied to the user's account and no one else will be authorized to use the ARK unless it's factory reset and reconfigured.

In an embodiment, the procedure for creating a user account and registering an ARK 110 with the cloud-based services 150 is a simple procedure.

-   -   user downloads ARK App;     -   the user Creates an account (using email, password) with ARK         Cloud-Based Services;     -   the ARK is placed in configuration mode;     -   the user adds the ARK to his/her account with ARK Cloud-Based         Services

In an embodiment, users can retrieve configuration information, history logs, change certain user profile settings from the ARK Cloud-Based Services 150. During configuration, a user is required to have a smartphone 130 or comparable mobile device with data connectivity. Thereafter, to view any transactional history, edit or change a user's profile they can access ARK Cloud-Based Services 150 using any type of device.

In various embodiments, the ARK Cloud-Based Services are easily scalable and as the demand grows so will the ARK Cloud-Based Services. Provisioning of cloud-based services, have become a standard in the industry providing fast data access and redundancy no matter the user's location.

In various embodiments, the ARK system 100 is designed to eliminate the need for vehicle owners to either contact a locksmith or visit a dealership to program a new key. It is a product with the intent purpose to remove not only the hassle and time, but to reduce the high costs involved in programing a vehicle's smart key.

FIG. 2 shows a block diagram providing a high-level view 200 of an embodiment of functions provided by an ARK App 210 in accordance with the present disclosure.

In an embodiment, when the ARK App 210 is first installed on a user's mobile device, a new user 220 is taken to a sign up process 230 whereby the user is registered with ARK servers 290 within the ARK Cloud-Based Services provided by various embodiments of the ARK system of the present disclosure.

After registration, the main menu 240 of the ARK App is displayed providing access to various functions 250, including configuration of the ARK (see FIG. 3), changing options on the ARK (see FIG. 4), operation of the ARK (see FIG. 5), and miscellaneous other options (see FIG. 6).

FIG. 3 shows a block diagram of an embodiment of a process 310 of configuring an ARK using an ARK App in accordance with the present disclosure.

In an embodiment, to configure an ARK device, configuration mode 310 is selected on the ARK App. In an embodiment, on the ARK device the user presses the lock/unlock button on the device for three seconds to place the device into configuration mode. The ARK App then recognizes that configuration is active 330. The ARK App then executes the appropriate configuration steps 340 to configure the ARK device to program a vehicle's fob interface 350 (within the vehicle's computer) to recognize the ARK. Note that the steps can be quite involved, and can vary based on vehicle type, make, and model. The user however sees the action performed in a single step on the ARK App. When configuration is complete 360, data relating to the configuration is stored on servers 390 within the ARK Cloud-Based Services.

FIG. 4 shows a block diagram of an embodiment of a process 400 of changing options relating to an ARK using an embodiment of ARK App in accordance with the present disclosure.

In an embodiment, the user using the ARK App selects a function for editing the ARK devices options 410. The user is then able to change various options 420, which in various embodiments includes changing the device name, changing the device passcode, and setting the device's operation mode, which could be secure or open. Other options may be supported. In an embodiment, when device options are changed, such changes are recorded on servers 490 provided by the ARK Cloud-Based Services.

FIG. 5 shows a block diagram of an embodiment 500 of the operation 510 of an ARK App and ARK device in accordance with the present disclosure.

In an embodiment, the ARK App can be used to issue commands 520 to the ARK device 530, which in turn, issue commands to a vehicle's fob interface. In an embodiment, the ARK device in turn communicates back to the ARK App with responses to such commands. Note that commands can originate with the ARK App or the ARK device.

FIG. 6 shows a block diagram of an embodiment 600 of options provided by an ARK App in accordance with the present disclosure.

In embodiment, when the user selects a function on the ARK App to select miscellaneous options 610, the user is able to access various options 620 relating to the ARK device or data stored on ARK Cloud-Based Services relating to the device. In various embodiments, such actions could include changing account settings, viewing device and account history, deactivating the device, as well as any other options in a particular embodiment.

FIG. 7 shows an embodiment 700 of an ARK 720 in accordance with the present disclosure attached to a smart phone case 710.

In the illustrated embodiment, the housing of the ARK 720 is attached to a conventional smart phone case 710. The housing of the ARK is attached to the smart phone case 710 by its base (not visible) using an adhesive pad (not visible). The housing of the ARK 720 has apertures 730, 740, and 750 for the buttons of a circuit board (not visible), the circuit board implementing functions to remotely lock and unlock the doors of an automobile, and to set off an alarm in the automobile.

FIG. 8 shows the ARK of FIG. 7 disassembled where the base of the ARK 760 is attached to a smart phone case 710 and the circuit board 800 that implements the functions of the ARK are visible.

The top of the housing of the ARK 720 is shown flipped over such that the underside of the housing is visible. The apertures 730, 740, and 750 can be seen as well. In this illustration, the circuit board 800 that implements the functions of the ARK is visible. The circuit board 800 has a button 810 that unlocks an automobile. The button 810 is accessible to a user through the aperture 730. The circuit board 800 further has a button 820 to unlock an automobile. The button 820 is accessible to a user through the aperture 740. The circuit board 800 further has a button 830 to start the automobile. The button 830 is accessible to a user through the aperture 750.

In this illustration, the base of the ARK 760 can be seen. The top of the housing of the ARK 720 snaps onto the base, with the circuit board 800 inside the housing of the ARK 720 such that the buttons 810, 820, and 830 are accessible through the respective apertures 730, 740, and 750 in the housing.

In the illustrative prototype, the base 760 is attached to the smart phone case 710 using an adhesive pad, however any other suitable means of attaching the base 760 to the smart phone case 710 could be used. In this example, the ARK 720 attached to the base provides the functions of unlocking and locking an automobile, starting the automobile, setting an alarm on the automobile, and other functions. Other devices can be attached to this base 760, or integrated fully into a case.

The base 760 can be attached to a wide variety of portable or stationary objects. A smart phone case 710 is one example of a portable object. Other examples of a portable object could be a laptop, a briefcase, or a tablet computer, or even another remote controller, such as a garage door opener. A stationary object could be a desk, a door, a wall, or a desktop computer.

In the illustrated embodiment, the circuit board 800 provides short range radio transmission capabilities to transmit coded signals to a receiver in the automobile which the ARK 720 is used to control (e.g. 315 MHz). In various embodiments, entry codes are encrypted and rotated to enhance security.

Depending on the capabilities of the circuit board 800, the ARK may have the capability to communicate with the device it is attached to and control functions on that device, or alternatively, be controlled by software, for example, a mobile app, on the device. Depending on the capabilities of the circuit board 800, communication may be via Wi-Fi, Bluetooth®, or near field communication.

In various other embodiments, the circuit board 800 could implement a user programmable computer to which a user could download software applications. For example, the circuit board 800 could implement an Android device. For example, in various other embodiments the ARK and the circuit board 800 could provide multiple buttons that are programmable, similar to a universal remote.

In the illustrated embodiment, the circuit board 800 provides click type buttons (e.g. have to be clicked using a pen) that provide the advantage that they are not easily pressed in the user's pocket. In various other embodiments, the buttons may take any suitable form now known or later to be developed in the art. In various other embodiments, the buttons of the ARK 720 could be in different colors for easy memorization of the functions provided by the buttons.

FIG. 9 shows another embodiment 900 of an ARK in accordance with present disclosure attached to a smart phone case 910.

In the illustrated embodiment, the base 970 of the ARK is attached to a conventional smart phone case 910 using an adhesive pad (not visible). The housing of the ARK 920 has buttons 930 (lock button), 940 (unlock button), 950 (open trunk button), and 960 (alarm button) that overlay switches on a circuit board (not shown), the circuit board implementing functions to remotely lock, and unlock the doors of an automobile, open the automobile's trunk, and to set off an alarm in the automobile.

FIG. 10 shows the base of the ARK of FIG. 9 from a side view attached to a smart phone case.

In the illustrative prototype, the base 970 is attached to the smart phone case 910 using an adhesive pad (not shown, however any other suitable means of attaching the base 970 to the smart phone case 910 could be used.) In this example, the ARK attached to the base provides the functions of unlocking and locking an automobile, starting the automobile, opening the truck of the automobile, and setting an alarm on the automobile. Other devices can be attached to this base 970, or integrated fully into a case 910 that acts as the ARK itself.

FIG. 11 shows various illustrative form factors 1100, 1200, and 1300 that can be used for an ARK in accordance with the present disclosure.

The illustration shows a black cylindrical form factor 1100, a white cylindrical form factor 1300, and white square form factor 1200, all of which could be attached to a smart phone case 1000 using any suitable means. In the illustrated embodiments, the ARK form factors 1100, 1200, and 1300 are fabricated using a hard plastic. The illustration also shows a flat passport/wallet form 1400 not attached to a smart phone case 1000; this flat form is suitable for attachment to a smartphone or other device where a streamlined form is desirable. The plastic could be any color beyond the colors illustrated herein. The various devices and form factors 1100, 1200, 1300 , and 1400 could be fabricated using any suitable material, for example, silicone, metal, or an impact and water resistant hard plastic capable of.

In the foregoing specification, the disclosure has been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. 

1. A platform for programming a vehicle's fob autonomously, functioning with a programmable remote transmitter device, comprising: the programmable remote transmitter device adapted to: wirelessly transmit commands to an onboard computer of the vehicle once the onboard wirelessly communicate with a user's mobile computing device separate from the remote transmitter device; an ODB2 peripheral device adapted to; operatively connect to the onboard computer of vehicle via an OBD2 port of vehicle; wirelessly communicate with the mobile computing device of the user; and provide vehicle information for the vehicle to the mobile device; at least one server hosting a service adapted to communicate with the user's mobile computing device, the service adapted to: receive user information from the mobile computing device of the user; receive user payment information from the mobile computing device of the user; verify the user's identity using the user information, the user payment information, and the vehicle information; register the user and the vehicle with the service; transmit programming instructions to the mobile computing device of the user for reprogramming the onboard computer's fob interface to recognize the programmable remote transmitter; an application comprising computer executable instructions that when installed on the mobile computing device, enables the mobile computing device to: receive user information from the user; receive user payment information from the user; receive vehicle information from the ODB2 peripheral; transmit the user information to the service; transmit the payment information to the service, cause the service to verify the user's identity using the user information, the user payment information, and the vehicle information, the cause the service to register the user and the vehicle with the service receive the programming instructions for reprogramming the onboard computer's fob interface to recognize the programmable remote transmitterd; and transmit the programming instructions to the programmable remote transmitter, and to the ODB2 peripheral, causing the programmable remote transmitter, and the ODB2 peripheral enabling the onboard computer's fob interface of the vehicle to recognize the programmable remote transmitter and to receive and respond to the commands directly from the programmable remote transmitter.
 2. The platform of claim 1 wherein the commands from the programmable remote transmitter comprise at least one of, but not limited to open the vehicle, lock the vehicle, start the vehicle, and open a truck of the vehicle.
 3. The platform of claim 2 wherein the application further enables the mobile computing device to enable the user of the mobile computing device to cause the remote transmitter to transmit at least one of the commands to the onboard computer of the vehicle using a user interface provided by the application on the mobile computing device.
 4. The platform of claim 3 wherein the ODB2 peripheral is further adapted to provide vehicle status information for the vehicle to the mobile device; and the application further enables the mobile computing device to display the vehicle status information on the user interface provided by the application on the mobile computing device.
 5. The platform of claim 4 wherein the application further enables the mobile computing device to retrieve and display a location of the programmable remote transmitter on the user interface provided by the application on the mobile computing device.
 6. The platform of claim 5 wherein the portable remote transmitter is in a housing that is adapted to be mounted on a surface.
 7. The platform of claim 6 wherein the surface is a back of a mobile device.
 8. The platform of claim 6 wherein the surface is a back of a smartphone case.
 9. The platform of claim 5 wherein the portable remote transmitter is in a housing that is in the form of a passport.
 10. The platform of claim 5 wherein the portable remote transmitter is in a housing that is in the form of a wallet.
 11. The platform of claim 2 wherein the portable remote transmitter has at least one button that, when pressed, cause the remote transmitter to transmit one of the commands to the onboard computer of the vehicle.
 12. The platform of claim 3 wherein the ODB2 peripheral is further adapted to delete at least a second remote transmitter from the onboard computer of the vehicle; and the application further enables the mobile computing device to display the vehicle status information on the user interface provided by the application on the mobile computing device.
 13. The platform of claim 3 wherein the portable remote transmitter is associated with the mobile device of the user such that the portable remote transmitter will not respond to commands issued by the application when installed on a second mobile user device.
 14. A platform for enabling a vehicle's fob interface to work with a programmable remote transmitter device, comprising: the programmable remote transmitter adapted to; wirelessly transmit commands to an onboard computer of a vehicle once the onboard computer's fob interface of has been identified and configured; and wirelessly communicate with a mobile computing device of a user that is separate the remote transmitter device; at least one server hosting a service adapted to communicate with the mobile computing device of the user, the service adapted to: receive user information from the mobile computing device of the user; receive user payment information from the mobile computing device of the user; receive vehicle information from the mobile computing device of the user; verify the user's identity using the user information, the user payment information, and the vehicle information, register the user and the vehicle with the service; transmit programming instructions to the mobile computing device of the user for deleting any previous programmed key codes and reprogramming the onboard computer'fob interface of the vehicle to recognize the programmable remote transmitter; and an application comprising computer executable instructions that when installed on the mobile computing device, enables the mobile computing device to; receive user information from the user; receive user payment information from the user; recieve vehicle information from the user; wirelessly communicate with the service on the at least one server; transmit the user information to the service; transmit the payment information to the service; transmit the vehicle information to the service; cause the service to verify the user's identity using the user information, the user payment information, and the vehicle information; cause the service to register the user and the vehicle with the service, receive the programming instructions for deleting any previous programmed key codes and reprogramming the onboard computer' of the vehicle to recognize the programmable remote transmitter; transmit the programming instructions to the programmable remote transmitter causing the programmable remote transmitter to delete any previously programmed key codes and reprogram the onboard computer of the vehicle to recognize the programmable remote transmitter and to receive and respond to the commands directly from the programmable remote transmitter.
 15. The platform of claim 14 wherein the commands from the programmable remote transmitter comprise at least one of open the vehicle, lock the vehicle, start the vehicle, and open a truck of the vehicle.
 16. The platform of claim 15 wherein the application further enables the mobile computing device to enable the user of the mobile computing device to cause the remote transmitter to transmit at least one of the commands to the onboard computer of the vehicle using a user interface provided by the application on the mobile computing device.
 17. The platform of claim 16 wherein the application further enables the mobile computing device to retrieve and display a location of the programmable remote transmitter on the user interface provided by the application on the mobile computing device.
 18. The platform of claim 17 wherein the portable remote transmitter is in a housing that is adapted to be mounted on a surface.
 19. The platform of claim 15 wherein the portable remote transmitter has at least one button that, when pressed, cause the remote transmitter to transmit one of the commands to the onboard computer of the vehicle.
 20. The platform of claim 16 wherein the portable remote transmitter is associated with the mobile device of the user such that the portable remote transmitter will not respond to commands issued by the application when installed on a second mobile user device. 